| Author |
Thread Statistics | Show CCP posts - 2 post(s) |
Primary This Rifter
4S Corporation
Goonswarm Federation
439
   |
Posted - 2015.01.05 22:29:05 -
[1] - Quote
"Ishtars are fine, but fighters definitely need a scan res nerf."
Reminder: CCP thinks you have no right to your alliance logos.
|
Primary This Rifter
4S Corporation
Goonswarm Federation
439
|
Posted - 2015.01.05 22:38:33 -
[2] - Quote
Panther X wrote:Primary This Rifter wrote:"Ishtars are fine, but fighters definitely need a scan res nerf." Really? Sheesh, here comes the short bus.
The quotation marks imply that that was CCP's thought process. I figured that was obvious.
Reminder: CCP thinks you have no right to your alliance logos.
|
Primary This Rifter
4S Corporation
Goonswarm Federation
439
|
Posted - 2015.01.05 22:43:48 -
[3] - Quote
I'm not entirely sure what the reasoning is for this change even having read the OP, but I'm pretty confident it has nothing to do with nerfing FB effectiveness against subcaps.
Reminder: CCP thinks you have no right to your alliance logos.
|
Primary This Rifter
4S Corporation
Goonswarm Federation
450
|
Posted - 2015.01.06 19:24:13 -
[4] - Quote
Mario Putzo wrote:Thats cute, but its not my problem if CCPs spaghetti code makes it hard for them to implement a new timer, that is CCP's problem and I can still expect them to actually fix what they claim they want to fix. Perhaps if they didn't spend the last 5 years kicking cans down the road they would have been able to streamline their code a bit more so they could overhaul aspects of the game they believe necessary to change. Keep in mind that this change is not only about DPS, but also avoiding server load. That server load is just as easily spiked with subcap drone usage as it it is with Capital drone usage. HED-GP?
I too would enjoy living in this fantasy world where "bad code" is the only thing preventing computers from doing everything you want them to.
Reminder: CCP thinks you have no right to your alliance logos.
|
Primary This Rifter
4S Corporation
Goonswarm Federation
450
|
Posted - 2015.01.06 19:38:03 -
[5] - Quote
Here's a question: do drones start flying towards a target before they finish locking it, or only once the target is locked?
If it's the former, then I don't really see how this will have that much of an effect unless you're sitting very close to your target.
If it's the latter, then yeah I can see how this would be annoying for FBs, but for fighters I don't think it'll really matter that much.
Reminder: CCP thinks you have no right to your alliance logos.
|
Primary This Rifter
4S Corporation
Goonswarm Federation
451
|
Posted - 2015.01.07 00:55:42 -
[6] - Quote
Mario Putzo wrote:Primary This Rifter wrote:Mario Putzo wrote:Thats cute, but its not my problem if CCPs spaghetti code makes it hard for them to implement a new timer, that is CCP's problem and I can still expect them to actually fix what they claim they want to fix. Perhaps if they didn't spend the last 5 years kicking cans down the road they would have been able to streamline their code a bit more so they could overhaul aspects of the game they believe necessary to change. Keep in mind that this change is not only about DPS, but also avoiding server load. That server load is just as easily spiked with subcap drone usage as it it is with Capital drone usage. HED-GP? I too would enjoy living in this fantasy world where "bad code" is the only thing preventing computers from doing everything you want them to. Making Abandon/Scoop/Recall to Drone bay trigger a timer is perfectly possible within the game. We see this already occurring in a broad spectrum of commands in game already (reload weapons for example). In fact we just saw them implement a new timer tied to Jump to Beacon commands, that didn't exist before. So the computer can be told to function to have a command also begin a timer. We also know that timers can be made to prevent someone from issuing commands again across a wide array of things. Which means locking drone commands based on a timer, is also a possible process in the game. If for any reason this can not be implemented due to code structure, than it is an issue with the code, not the process capability of the game. So yes, if it can not be implemented, it is because of bad code, period.
It's not about code structure, it's about computing resources.
Keeping track of these timers would increase server load, which goes against part of CCP's intent for this change.
Reminder: CCP thinks you have no right to your alliance logos.
|
| |
|